-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add and configure Sentry gem #146
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know you didn't request a review yet, but you had mentioned in slack this was running so I did a review before I realized it was still a draft. Sorry if it wasn't ready!
config/initializers/sentry.rb
Outdated
return unless ENV.has_key?('SENTRY_DSN') | ||
config.dsn = ENV.fetch('SENTRY_DSN') | ||
config.breadcrumbs_logger = [:active_support_logger, :http_logger] | ||
config.enable_tracing = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not enable tracing via Sentry at this time. We should get the same/similar data via Scout. If we want to move that to Sentry instead we can discuss, but don't need to have both on for now.
Gemfile
Outdated
@@ -69,6 +69,11 @@ gem 'rack-cors' | |||
# Use Redis adapter to run Action Cable in production | |||
# gem "redis", ">= 4.0.1" | |||
|
|||
# Sentry integration according to their documentation [https://docs.sentry.io/platforms/ruby/guides/rails/] | |||
gem "stackprof" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stackprof
is only required if we enable profiling and/or tracing. I think for now we should leave both off and remove this gem.
No worries - the big reason this wasn't in review yet was because I was wanting to troubleshoot why the messages weren't showing up in Slack yet. That doesn't seem like something that would affect these code changes, though. |
This adds the Sentry integration, similarly to what we've done with other applications and the current Sentry documentation.
Developer
Ticket(s)
https://mitlibraries.atlassian.net/browse/TCO-88
Accessibility
all issues introduced by these changes have been resolved or opened
as new issues (link to those issues in the Pull Request details above)
Documentation
ENV
Stakeholders
Dependencies and migrations
YES dependencies are updated
NO migrations are included
Reviewer
Code
added technical debt.
Documentation
(not just this pull request message).
Testing